Community Template
The Light Weight Scrum Process
Template is a light-weight and scrum
oriented process template for Team
Foundation Server. The objective of
the community initiative developed
and maintained by evangelists and
MVPs of the VSTS/TFS product and the
scrum methodology, is a process
template that allows teams to adapt
their ecosystem to deliver frequent
and regular high quality software
and business value.
Process Overview
The Lightweight Scrum process template is focused on delivering
high quality solutions, using a low-impact, visual and team collaboration
process.
At the beginning of a project the project stakeholders create a
prioritized and up-to-date product backlog, using user stories. These user
stories drive the creation of backlog items. The product
team is then able to select a set of highest priority backlog items in a sprint
planning meeting and associating them with sprints. While the product team
proceeds to work through the list of backlog items assigned to the current
sprint, daily scrum meetings ensure that the team communicates and synchronizes
their activities. At the end of each sprint the team demonstrates the sprint
products to all product stakeholders, capturing and prioritizing feedback during
the Sprint Review meeting. The final step in each sprint is a Sprint
Retrospective meeting, during which the team discuss how to improve the team
environment and process, in other words the team ecosystem, in subsequent
sprints.
Contacts
For more information, please visit:
http://www.codeplex.com/vstsscrum
Contributors
Willy-Peter Schaub
Mike Azocar
Steven Borg

Thanks to all who helped with Light Weight Scrum!
|  | Visual Studio Team SystemVisual Studio Team System provides tools that you can use to enact process guidance.
Terminology
-
Process Guidance
The Light Weight Scrum Process Template is a light-weight and scrum process template for Team Foundation Server.
-
Project Portal
The Project Portal stores artifacts such as documents, spreadsheets, and
project plans.
-
Roles
Solution team members assume one or more roles as defined below.
-
Source Control
The Team Foundation version control system stores artifacts such as source
code and text.
-
Sprints and Items
Team members work on backlog items and a sprint defines a set of backlog
items that must be completed during the sprint defined period of time.
-
Users and Groups
Each team member belongs to one or more groups, which enforce security
privileges.
-
Visual Studio Team System
Visual Studio Team System provides tools and an environment that you can use
to interact with the process guidance.
-
Work Item Database
All backlog items are recorded in a database, also known as the work item
database. You can investigate the solution health and status by querying
these backlog items and their state in real time.
-
Work Products
Work products include artifacts such as documents, spreadsheets, project
plans, source code, and other tangible entities.
Roles

-
Analyst
An analyst defines the business opportunity and business processes,
providing business subject matter expertise to the team.
-
Architect
An architect investigates and defines the foundations of the
solution, including operational, infrastructure and solution architectures,
by dividing the system into separate and autonomous subsystems.
-
Developer
A developer implements the solution as specified by the solution
specifications. During sprint planning a developer is also involved with the
estimation of time and effort, as well as planning.
-
Project Manager
A project manager is focused on ensuring that the team delivers
business value within the agreed schedule and budget. Apart from scheduling
and planning, the project manager is also responsible for ensuring that the
team has a “happy” and productive ecosystem.
-
Release Manager
A release manager plans and manages the release and deployment of
the solution.
-
Scrum Master
A Scrum Master is responsible for ensuring that the team operates
by the practices of Scrum, protects the team against over commitment and
scope creep and facilitates the daily scrum. A Scrum Master is not a project
manager.
-
Tester
A tester is responsible for discovering and communicating issues
with the solution, as well as reporting all issues accurately and assisting
the developers with the resolution of the issues. Tests include positive
testing to validate that the solution meets the agreed business
specifications, and negative testing to identify stability, reliability and
functional discrepancies in the solution.
|